<?php
/**
 * <https://y.st./>
 * Copyright © 2017 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'<{title}>' => 'Finishing up for the week',
	'takedown' => '2017-11-01',
	'<{body}>' => <<<END
<img src="/img/CC_BY-SA_4.0/y.st./weblog/2017/10/18.jpg" alt="Local trees across the street" class="framed-centred-image" width="800" height="480"/>
<section id="general">
	<h2>General news</h2>
	<p>
		My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
	</p>
</section>
<section id="university">
	<h2>University life</h2>
	<p>
		I finished my discussion assignment for the week:
	</p>
	<blockquote>
		<p>
			You make a very good point about applications demanding more memory these days.
			Some of it is because our hardware keeps improving, so making the most of that hardware involves using what we now have to create a better experience.
			However, some of the newer software seems to use more memory to create a <strong>*worse*</strong> experience.
			Things such as transparent window frames aren&apos;t overly obnoxious by any means, but they&apos;re ugly and take more system resources to create than good-looking, solid window frames.
		</p>
		<p>
			As hardware capacity increases, it makes sense overhead for managing it is going to increase as well.
			Not only do we have more pages to manage, we also have a bigger hardware memory itself to manage.
			As we learned with caches, having fast memory requires having <strong>*small*</strong> memory.
			As we increase our $a[RAM] size, we&apos;re going to see a reduction in $a[RAM] speed unless we find some way to counter that reduction.
			The translation-lookahead buffer misses you mentioned are definitely a problem for our speed, and they&apos;re only made worse by the larger, slower memory that is already causing the misses.
			In other words, not only are translation-lookahead buffer misses going to happen more often, they&apos;re also going to be more costly, as finding the address-translation data in $a[RAM] is going to take more time than before.
			The redundant memory mappings you researched could prove very valuable in reducing the number of translation-lookahead buffer misses though, hopefully keeping computers fast and responsive.
		</p>
	</blockquote>
</section>
END
);
